Litigation Details for Finjan, Inc. v. Blue Coat Systems, Inc. (N.D. Cal. 2015)

Finjan, Inc. v. Blue Coat Systems, Inc. (N.D. Cal. 2015)

Docket		Date Filed	2015-07-15
Court	District Court, N.D. California	Date Terminated	2018-03-05
Cause	15:1126 Patent Infringement	Assigned To	Beth Labson Freeman
Jury Demand	Both	Referred To	Susan G. Van Keulen
Patents	10,174,017
Link to Docket	External link to docket

Details for Finjan, Inc. v. Blue Coat Systems, Inc. (N.D. Cal. 2015)

Date Filed	Document No.	Description	Snippet	Link To Document
2015-07-15				External link to document

Finjan, Inc. v. Blue Coat Systems, Inc. | 5:15-cv-03295 Litigation Summary and Patent Analysis

Last updated: August 20, 2026

Finjan won a jury verdict of approximately $39.5 million against Blue Coat Systems in the Northern District of California for infringement of four cybersecurity patents. The case involved Blue Coat’s ProxySG secure web gateway and related malware-detection products. The Federal Circuit later affirmed the core infringement and validity findings. The dispute established a significant damages award for software-security patents based on a reasonable-royalty analysis tied to Blue Coat’s product revenue. [1][2]

What was Finjan v. Blue Coat Systems about?

Finjan alleged that Blue Coat’s web-security products infringed patents covering the detection, classification, monitoring, and blocking of malicious computer code delivered through network traffic.

The asserted technology addressed a security workflow in which:

1. A downloadable object or executable code is identified.
2. The object is analyzed for malicious behavior or characteristics.
3. A security profile or verdict is generated.
4. The security result is used to permit, block, or monitor the object.

Blue Coat’s accused products included the ProxySG secure web gateway and Content Analysis systems. Blue Coat argued that its products did not practice the asserted claim limitations and that portions of the patents were invalid.

Finjan filed the action on June 11, 2015, in the U.S. District Court for the Northern District of California. The case was assigned docket number 5:15-cv-03295 and was handled by Judge Beth Labson Freeman. [1]

Which patents did Finjan assert against Blue Coat?

Finjan asserted four U.S. patents directed to computer security systems and malicious-code detection.

Patent	General subject matter	Litigation role
U.S. Patent No. 6,154,844	Protecting computers and networks from hostile downloadables	Asserted against Blue Coat’s security products
U.S. Patent No. 6,804,780	Computer security systems and methods	Asserted against malware-detection functionality
U.S. Patent No. 7,613,926	Runtime monitoring of malicious mobile code	Asserted against behavioral or code-monitoring functions
U.S. Patent No. 8,141,154	Detecting and analyzing malicious code	Asserted against Blue Coat’s malware-scanning architecture

The patent family was associated with Finjan’s broader portfolio covering software-based network security, downloadable-code analysis, security profiles, and runtime monitoring. Several patents originated from applications filed in the late 1990s and early 2000s, giving the litigation a significant patent-term and priority-date component.

What claims were at issue?

The Federal Circuit opinion identifies asserted claims across all four patents. The dispute focused on limitations involving:

• “Downloadables”
• Software components or executable code
• Security profiles
• Malware detection
• Runtime monitoring
• Communication between a protection system and a protected computer
• Use of a generated security result to control access or execution

The parties disagreed over whether the claim language covered Blue Coat’s use of cloud-based or gateway-based analysis rather than protection performed solely on an end user’s computer.

What was the jury verdict in Finjan v. Blue Coat?

The jury found that Blue Coat infringed claims from all four asserted patents and awarded Finjan approximately $39.5 million in damages. The award was based on a reasonable royalty rather than lost profits.

The jury rejected Blue Coat’s principal invalidity defenses, including arguments based on anticipation and obviousness. The verdict therefore addressed both infringement and patent validity.

Issue	Jury result
Infringement of the ’844 patent	Found
Infringement of the ’780 patent	Found
Infringement of the ’926 patent	Found
Infringement of the ’154 patent	Found
Patent invalidity defenses	Rejected on the principal asserted grounds
Damages	Approximately $39.5 million
Damages theory	Reasonable royalty

The damages analysis was important because Finjan’s expert used Blue Coat’s product revenues and prior licensing evidence to support royalty rates. The Federal Circuit later reviewed the damages methodology and upheld the judgment. [2]

How did the Federal Circuit rule?

The Federal Circuit affirmed the district court judgment in Finjan’s favor in Finjan, Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299 (Fed. Cir. 2018). [2]

The appellate court upheld the district court’s treatment of several disputed claim terms and rejected Blue Coat’s challenges to the infringement findings. The court also upheld the validity determinations and the damages award.

What claim-construction issues did the Federal Circuit address?

The appeal involved the scope of terms used in the asserted patents, including “downloadable” and related security-system concepts.

Blue Coat argued that Finjan’s claim constructions improperly expanded the patents beyond the disclosed computer-security architecture. Finjan argued that the claims covered network-based and gateway-based security implementations, including systems in which analysis occurs before content reaches an endpoint.

The Federal Circuit accepted the broader technical application of the claim language where supported by the patent specifications and prosecution history. The ruling did not limit the asserted patents to a narrow endpoint-only implementation.

Why was the damages ruling significant?

The damages ruling allowed Finjan to rely on product revenue associated with the accused security systems rather than proving that every dollar of product revenue came from the patented feature.

The court accepted the jury’s reasonable-royalty framework, which considered:

• Blue Coat’s sales of accused products
• The commercial role of malware-detection functionality
• Comparable licensing evidence
• The parties’ hypothetical negotiation
• The value of the patented technology in the overall product

The Federal Circuit’s approval strengthened Finjan’s negotiating position in later patent licensing discussions involving cybersecurity companies.

What patent expiration dates affected the case?

The relevant patent terms were constrained by the priority and filing dates of the underlying patent families. The nominal term dates were substantially earlier than the issuance dates of some continuation patents.

Patent	Earliest family timing	Approximate nominal term endpoint
’844 patent	December 1997 filing period	December 2017, subject to patent-term adjustment
’780 patent	June 1997 priority period	June 2017, subject to patent-term adjustment
’926 patent	Continuation family associated with earlier filings	Generally tied to the earlier family term
’154 patent	Early-2000 filing period	Approximately 2020, subject to patent-term adjustment

The exact enforceability period depended on patent-term adjustment, terminal disclaimers, and the specific family relationship reflected in the USPTO records. The expiration issue reduced the practical value of injunctive relief and increased the importance of monetary damages.

What was the Orange Book status of the Finjan patents?

The patents in Finjan v. Blue Coat were software and cybersecurity patents, not patents covering FDA-approved drugs. They were not Orange Book-listed patents and were not subject to Hatch-Waxman Paragraph IV litigation.

There was no FDA approval, New Drug Application, Abbreviated New Drug Application, biologic license application, or biosimilar pathway involved in the case.

Regulatory issue	Status
FDA product approval	Not applicable
Orange Book listing	None
Paragraph IV challenge	None
Biosimilar litigation	None
Small-molecule generic entry	None
Relevant market	Enterprise cybersecurity software

The competitive risk analysis therefore concerns software product redesign, licensing, injunction exposure, and patent expiration rather than generic or biosimilar entry.

Did Blue Coat file a Paragraph IV challenge?

No. Paragraph IV certifications apply to drug patents listed in the FDA Orange Book. Blue Coat’s case involved enterprise cybersecurity software and did not use the Hatch-Waxman framework.

Blue Coat challenged the patents through standard district-court invalidity defenses and Federal Circuit appellate review.

Which companies were connected to the Blue Coat litigation?

Blue Coat was acquired by Symantec in 2016 for approximately $4.65 billion. The acquisition placed Blue Coat’s cybersecurity product portfolio and associated litigation exposure within Symantec’s corporate structure. [3]

The corporate transition mattered because the accused products, licensing negotiations, and potential enforcement obligations continued after the acquisition. Symantec later became part of Broadcom following Broadcom’s acquisition of Symantec’s enterprise-security business in 2019. [4]

Company	Role
Finjan, Inc.	Patent owner and plaintiff
Blue Coat Systems, Inc.	Accused infringer and defendant
Symantec Corp.	Blue Coat acquirer
Broadcom Inc.	Subsequent acquirer of Symantec’s enterprise-security business

The acquisition history complicated the commercial analysis but did not eliminate liability for the pre-acquisition infringement adjudicated in the case.

What litigation issues affected the outcome?

Patent validity

Blue Coat challenged the asserted patents under Section 102 and Section 103 of the Patent Act. The jury rejected the principal invalidity theories. The Federal Circuit did not disturb those findings.

The patents survived because Finjan presented evidence that the prior art did not disclose the claimed combination of downloadable-code analysis, security-profile generation, and protection or monitoring functions.

Infringement

Finjan relied on technical evidence concerning Blue Coat’s product architecture, including the interaction among:

• ProxySG appliances
• Content Analysis systems
• Malware scanning
• Web content classification
• Security verdicts
• Endpoint or network enforcement

The litigation demonstrates that infringement can turn on system interactions rather than a single isolated software module. Blue Coat’s argument that analysis occurred in a different location from the protected computer did not defeat the verdict.

Damages

The jury awarded a reasonable royalty. Finjan did not need to establish that Blue Coat’s entire product value came from the patented features. The damages evidence instead linked the patents to commercially relevant security functions and product sales.

The approximately $39.5 million award represented a substantial percentage of the value Finjan attributed to the accused product lines, but the reported judgment was not based on a permanent royalty obligation for all future sales.

Injunctive relief

The approaching expiration of several asserted patents weakened the practical case for a long-term injunction. Monetary relief was the principal economic remedy. The Federal Circuit’s affirmance preserved the damages judgment and the associated patent findings.

Was there a settlement agreement after the verdict?

Public reporting and Finjan’s later corporate disclosures describe subsequent licensing and settlement activity involving major cybersecurity companies, including Symantec. The litigation record, however, should be distinguished from later portfolio-wide commercial agreements.

The reported district-court verdict and Federal Circuit judgment are the central adjudicated outcomes in docket 5:15-cv-03295. A later license or settlement involving Finjan and a corporate successor would not erase the court’s infringement findings unless the agreement expressly resolved the judgment and related obligations.

How strong was Finjan’s patent estate after the Blue Coat case?

Finjan’s estate had meaningful enforcement value in cybersecurity software because the patents covered recurring functions used across web gateways, endpoint protection, malware analysis, and network security products.

Its strengths included:

• A portfolio directed to core malware-detection workflows
• Multiple related patents covering overlapping system architectures
• Evidence supporting licensing negotiations
• A favorable jury verdict against a major security vendor
• Federal Circuit confirmation of key infringement and damages findings

Its constraints included:

• Older priority dates
• Imminent or completed patent expirations for several asserted patents
• The need to prove claim-specific implementation in each accused product
• The risk that product redesign could avoid particular claim limitations
• Limited value from patents after expiration

The portfolio was stronger as a licensing and damages asset than as a long-term exclusionary asset for the patents asserted in this case.

What generic-entry risks existed for Blue Coat’s products?

The case did not involve generic drugs. The relevant entry risks were:

Risk	Assessment
Immediate product injunction	Reduced by patent expiration and monetary-relief posture
Continued damages exposure	Material through the enforceable patent terms
Product redesign	Possible, depending on claim limitations
Licensing cost	Material after the verdict and appellate affirmance
Competitor patent countersuits	A potential strategic response
Post-expiration patent risk	Dependent on unasserted continuation or later-filed patents

For enterprise-security companies, the principal lesson was that a product can face infringement exposure even when the patented function is integrated into a broader security platform and performed across multiple network components.

How does Finjan v. Blue Coat compare with pharmaceutical patent litigation?

Finjan v. Blue Coat differs fundamentally from pharmaceutical patent disputes.

Category	Finjan v. Blue Coat	Pharmaceutical Hatch-Waxman case
Product	Cybersecurity software and appliances	Drug product
Patent listing	No Orange Book listing	Orange Book listing may apply
Generic challenge	None	Paragraph IV certification
FDA role	None	Central to approval and exclusivity
Damages	Reasonable royalty for software sales	Lost profits or royalty for drug sales
Injunction	Patent-based software relief	Often tied to generic approval timing
Biosimilar risk	None	Applies to biologic products

The case is relevant to technology licensing, software freedom-to-operate analysis, acquisition diligence, and patent monetization. It has no direct FDA exclusivity or biosimilar implications.

Key Takeaways

• Finjan sued Blue Coat in 2015 in the Northern District of California under docket 5:15-cv-03295.
• The asserted patents covered malicious-code detection, downloadable content, security profiles, and runtime monitoring.
• A jury found infringement of four patents and awarded approximately $39.5 million.
• The Federal Circuit affirmed the principal infringement, validity, and damages findings in 2018.
• The case involved no FDA approval, Orange Book listing, Paragraph IV challenge, generic drug, or biosimilar.
• Blue Coat’s acquisition by Symantec and Symantec’s later enterprise-security transfer to Broadcom expanded the commercial significance of the dispute.
• The patents had older priority dates, making patent-term limitations and damages more important than long-term injunctive relief.
• Finjan’s outcome strengthened its licensing leverage across the cybersecurity industry.

FAQs

What was the final damages award in Finjan v. Blue Coat?

The jury awarded Finjan approximately $39.5 million in reasonable royalties for infringement of four cybersecurity patents. The Federal Circuit affirmed the core damages judgment.

Did Finjan win all of its patent claims against Blue Coat?

Finjan prevailed on the asserted claims submitted to the jury across four patents. The verdict included findings of infringement and rejected the principal invalidity defenses.

Did Symantec inherit Blue Coat’s patent litigation exposure?

Symantec acquired Blue Coat in 2016. The acquisition placed Blue Coat’s products and litigation obligations within Symantec’s corporate structure, subject to the terms of the acquisition and subsequent resolutions.

Were the Finjan patents still enforceable after 2020?

Several asserted patents had priority dates in the late 1990s or early 2000s, so their nominal terms were largely exhausted by 2017 to 2020, subject to patent-term adjustment and family-specific details.

Does the Blue Coat decision affect cybersecurity software freedom-to-operate reviews?

Yes. The decision shows that patent analysis must examine distributed software functions, gateway processing, malware verdicts, security profiles, and interactions between network and endpoint components rather than reviewing only standalone modules.

References

1. Finjan, Inc. v. Blue Coat Systems, Inc., No. 5:15-cv-03295, U.S. District Court for the Northern District of California, docket proceedings.

2. Finjan, Inc. v. Blue Coat Systems, Inc., 879 F.3d 1299 (Fed. Cir. 2018).

3. Symantec Corporation. (2016). Symantec completes acquisition of Blue Coat Systems. Corporate transaction announcement.

4. Broadcom Inc. (2019). Broadcom completes acquisition of Symantec’s enterprise security business. Corporate transaction announcement.

5. U.S. Patent and Trademark Office. (n.d.). Patent records for U.S. Patent Nos. 6,154,844, 6,804,780, 7,613,926, and 8,141,154. Implements the Patent Center and Patent Examination Data System records.